JP7169827B2 - Terminal and communication method - Google Patents

Description

The present invention relates to a terminal and communication method in a wireless communication system.

In the 3GPP (3rd Generation Partnership Project), 5G or NR (New Radio) will be used in order to further increase system capacity, further increase data transmission speed, and further reduce delay in wireless sections. A wireless communication system called "5G" (hereinafter, the wireless communication system is referred to as "5G" or "NR") is under study. In 5G, various radio technologies are being studied in order to meet the requirements of realizing a throughput of 10 Gbps or more and keeping the delay in the radio section to 1 ms or less.

In NR, 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core) which is the core network in LTE (Long Term Evolution) network architecture and E-UTRAN (RAN (Radio Access Network) in LTE network architecture ( A network architecture including NG-RAN (Next Generation-Radio Access Network) corresponding to Evolved Universal Terrestrial Radio Access Network (NG-RAN) is under study (for example, Non-Patent Document 1).

3GPP TS 23.501 V15.2.0 (2018-06)

Among operators that have not adopted a roaming architecture, it has been difficult for users to connect to network slices constructed by operators other than the operator that serves as HPLMN (Home Public Land Mobile Network).

SUMMARY OF THE INVENTION The present invention has been made in view of the above points, and it is an object of the present invention to facilitate users' network connection for operators that do not adopt roaming architecture.

According to the disclosed technology, a communication unit that communicates with another terminal , a control unit that determines whether or not the other terminal can connect to a network slice, and the other terminal can connect to the network slice. , a transmission unit that transmits the communication packet transmitted from the other terminal to the network slice, and if the other terminal is connectable to the network slice, transmits the communication packet from the network slice to the other terminal a receiving unit for receiving a communication packet, and in the determination, a PLMN (Public Land Mobile Network) ID notified from the other terminal and a PLMN ID connectable to the network slice acquired during network registration processing; If they match, it is determined that the other terminal is connectable to the network slice, and the PLMNID notified from the other terminal is stored in association with the MAC (Media Access Control) address of the other terminal. , a terminal that determines a network slice for transmitting a communication packet based on a MAC address included in the communication packet transmitted from the other terminal .

According to the disclosed technique, it is possible to facilitate user network connection for operators that do not employ a roaming architecture.

1 is a diagram for explaining an example of a radio communication system according to an embodiment of the present invention; FIG. FIG. 3 is a sequence diagram for explaining an operation example (1) of the wireless communication system according to the embodiment of the present invention; FIG. 4 is a sequence diagram for explaining an operation example (2) of the wireless communication system according to the embodiment of the present invention; 1 is a diagram showing an example of functional configuration of a network node 10 according to an embodiment of the present invention; FIG. 2 is a diagram showing an example of a functional configuration of user device 20 according to an embodiment of the present invention; FIG. 2 is a diagram showing an example of a hardware configuration of network node 10 or user device 20 according to an embodiment of the present invention; FIG.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

Existing technologies are appropriately used for the operation of the wireless communication system according to the embodiment of the present invention. However, the existing technology is, for example, existing LTE, but is not limited to existing LTE. In addition, the term "LTE" used in this specification, unless otherwise specified, has a broad meaning including LTE-Advanced and LTE-Advanced and subsequent systems (eg: NR), or wireless LAN (Local Area Network). shall have

Further, in the embodiment of the present invention, "configuring" wireless parameters and the like may mean that predetermined values are set in advance (pre-configure), or the network node 10 or It may be that wireless parameters notified from the user device 20 are set.

FIG. 1 is a diagram for explaining an example of a radio communication system according to an embodiment of the invention. As shown in FIG. 1, the radio communication system according to the embodiment of the present invention has a network composed of user equipments 20, UE-A and UE-B, and a plurality of network nodes . UE-A is a UE (User Equipment) having a contract with Carrier A (“Carrier” is also called “Business Operator” or “Operator”), and can connect to Carrier A's network. Furthermore, UE-A can be connected to another user device 20 via an interface such as a wireless LAN (Local Area Network) or a wired LAN. UE-B is a UE that has a subscription with Carrier B and is able to connect to Carrier B's network. UE-B is also authorized to connect to Carrier A's network.

The network includes network nodes 10 having one or more functions. Hereinafter, one network node 10 corresponds to each function, but one network node 10 may realize a plurality of functions, or a plurality of network nodes 10 may realize one function. . Also, the "connection" described below may be a logical connection or a physical connection.

RAN (Radio Access Network) is a network node 10 having a radio access function, and is connected with UE-A, AMF (Access and Mobility Management Function) and UPF (User plane function). The AMF is a network node 10 having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 10 having functions such as a PDU (Protocol Data Unit) session point to the outside interconnected with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling.

AMF is connected with UE-A, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), and PCF (Policy Control Function). AMF, SMF, NSSF, NEF, NRF, PCF are network nodes 10 interconnected via respective service-based interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Npcf. N1, N2, N3, N4, and N6 indicate reference points between network nodes 10. FIG.

The SMF has functions such as session management, UE IP (Internet Protocol) address assignment and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NSSF is a network node 10 that has functions such as selecting a network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. be. A NEF is a network node 10 having a function of notifying other NFs (Network Functions) of capabilities and events. The NRF is a network node 10 that has the function of discovering services and providing service information upon request from the NF. A PCF is a network node 10 having a function of performing network policy control.

Here, as a use case, for example, an operator may construct a network slice for an event held in a specific area or time (eg, sporting event, etc.). When a user other than the user who has a contract with the operator connects to the network slice, HPLMN (Home PLMN) and VPLMN (Visited PLMN) using the standardized roaming architecture N32 interface are adopted. It becomes necessary to be However, not all operators have adopted a roaming architecture. Therefore, it is assumed that users cannot connect to network slices constructed by different operators between operators that do not adopt a roaming architecture.

Therefore, a user device 20 that has a contract with a certain operator relays the communication of the user device 20 that has a contract with another operator, so that the network slice constructed by the operator with which the own device has a contract is transferred to another operator. A user device 20 contracted with an operator is connected. That is, users under contract with other operators can be easily and appropriately accommodated in the network slice constructed by the operator under contract with the own device.

In FIG. 2, UE-A is a UE with a carrier A contract and UE-B is a UE with a carrier B contract. UE-A and UE-B can be connected by tethering via a wired or wireless LAN. UE-A can connect to network slice Slice #n included in the network service provided by carrier A. For example, Slice#n accommodates users for sporting events. UE-A can establish a PDU session with UPF. By relaying the communication packet of UE-B by UE-A, UE-B can connect to network slice Slice #n provided by carrier A by using the PDU session of UE-A.

The communication medium connecting UE-A and UE-B may be any communication medium, including the above wired or wireless LAN. UE-A becomes a gateway device or a device performing tethering to UE-B.

When UE-B connects to UE-A, UE-B sends the PLMNID to UE-A. UE-A may check whether UE-B is authorized to connect to the network slice provided by carrier A with that PLMNID. For example, an administrator may decide which carrier's UEs should be connected to carrier A's network slice. UE-A may determine whether to allow UE-B to connect to the network slice by referring to the whitelist or blacklist based on the PLMN ID. Also, for example, if the communication medium is a wireless LAN, based on the ANQP (Access Network Query Protocol) parameters defined in Passpoint transmitted by UE-B, UE-A is connected to the network slice of carrier A It may be determined whether ANQP parameters include 3GPP Cellular Network Information, Domain Name List, NAI (Network Access Identifier) Realm List, and the like.

In addition, the UE-A relays and analyzes the communication packet transmitted by the UE-B, thereby connecting to an appropriate network slice. For example, the network slice of the connection destination is determined by referring to the table held by UE-A from the communication packet. The table includes, for example, FQDNs (Fully Qualified Domain Names), IP addresses, port numbers, DSCP (Differentiated Services Code Point) values, etc. of communication packets.

UE-B may establish one or more connections to one or more network slices for which UE-A is entitled to connect. UE-A has a table that manages the connection to the relaying UE-B's network slice. Details of the table will be described later. When UE-A terminates the network slice connection, UE-B's network slice connection is also terminated.

FIG. 2 is a sequence diagram for explaining the operation example (1) of the wireless communication system according to the embodiment of the present invention. From step S11 to step S14 shown in FIG. 2, UE registration of UE-A is performed. In step S11, UE-A transmits a "Registration request" including NSSAI to AMF via RAN. Subsequently, the AMF transmits a Slice Selection request including the NSSAI and PLMNID to the NSSF (S12).

In step S13, the NSSF sends the NSI ID (Network Slice Instance Identifier), Allowed S-NSSAI (Single Network Slice Selection Assistance Information), AMF address, Allowed PLMNID and Forbidden PLMNID to the AMF. Subsequently, the AMF transmits a "Registration accept" including Allowed S-NSSAI, AMF address, Allowed PLMNID and Forbidden PLMNID to UE-A via RAN (S14). The UE registration of UE-A is completed in steps S11 to S14. Allowed PLMNID is a PLMNID that permits connection among PLMNIDs transmitted from UE-B, and Forbidden PLMNID is a PLMNID that prohibits connection.

In step S15, UE-A holds PLMNIDs of connectable other carriers for each S-NSSAI. Tables 1 to 4 are examples of Table 1 created and stored by UE-A in step S15.

As shown in Table 1, 'S-NSSAI', 'PDU session', 'communication packet port number' and 'slice accommodation permission PLMN ID' are associated and stored. "S-NSSAI" corresponds to each network slice "Slice#n". "Slice accommodation permission PLMNID" is a PLMNID that permits accommodation in the corresponding Slice #n among the PLMNIDs transmitted from UE-B, and may be the Allowed PLMNID received in step S14, or may be specified in advance. It may also be a PLMNID. "PDU session" identifies a PDU session established in the corresponding Slice #n. "Communication packet port number" identifies the port number of the communication packets of the corresponding PDU session.

As shown in Table 2, 'S-NSSAI', 'PDU session', 'communication packet DSCP value' and 'slice accommodation permission PLMN ID' are associated and stored. "S-NSSAI" corresponds to each network slice "Slice#n". "Slice accommodation permission PLMNID" is a PLMNID that permits accommodation in the corresponding Slice #n among the PLMNIDs transmitted from UE-B, and may be the Allowed PLMNID received in step S14, or may be specified in advance. It may also be a PLMNID. "PDU session" identifies a PDU session established in the corresponding Slice #n. "Communication packet DSCP value" identifies the DSCP value of the corresponding PDU session.

As shown in Table 3, 'S-NSSAI', 'PDU session', 'communication packet destination IP address' and 'slice accommodation permission PLMN ID' are associated and stored. "S-NSSAI" corresponds to each network slice "Slice#n". "Slice accommodation permission PLMNID" is a PLMNID that permits accommodation in the corresponding Slice #n among the PLMNIDs transmitted from UE-B, and may be the Allowed PLMNID received in step S14, or may be specified in advance. It may also be a PLMNID. "PDU session" identifies a PDU session established in the corresponding Slice #n. "Communication Packet Destination IP Address" identifies the destination IP address of the corresponding PDU session.

As shown in Table 4, "S-NSSAI", "PDU session", "communication packet FQDN" and "slice accommodation permission PLMN ID" are associated and stored. "S-NSSAI" corresponds to each network slice "Slice#n". "Slice accommodation permission PLMNID" is a PLMNID that permits accommodation in the corresponding Slice #n among the PLMNIDs transmitted from UE-B, and may be the Allowed PLMNID received in step S14, or may be specified in advance. It may also be a PLMNID. "PDU session" identifies a PDU session established in the corresponding Slice #n. "Communication packet FQDN" identifies the FQDN of the corresponding PDU session.

In steps S21 and S22, UE-A establishes a PDU session. In step S21, UE-A transmits a "PDU session request" including S-NSSAI to AMF via RAN. AMF then sends a “PDU session create request” to UPF via SMF. In step S22, the UPF sends a 'PDU session create response' to the AMF via the SMF. AMF then sends a 'PDU session accept' to UE-A via the RAN. A PDU session is established between UE-A and UPF by steps S21 and S22.

FIG. 3 is a sequence diagram for explaining an operation example (2) of the wireless communication system according to the embodiment of the present invention. After the PDU session is established between UE-A and UPF, UE-A sends a service notification Beacon to UE-B in step S31. Here, the communication medium between UE-A and UE-B is assumed to be a wireless LAN, but other communication mediums may be used. Subsequently, UE-B sends an automatic connection request, which is an ANQP query notification, to UE-A (S32). Subsequently, UE-A sends an automatic connection response, which is an ANQP query response, to UE-B (S33). UE-B then sends an authentication request including the PLMNID notification to UE-A (S34).

In step S35, UE-A retains the notified MAC address and PLMNID of UE-B. Table 5 is an example of Table 2 created and stored by UE-A in step S35.

As shown in Table 5, terminal IDs (MAC addresses) and PLMN IDs are associated and held.

In step S36, UE-A sends an authentication complete to UE-B and a connection is established between UE-A and UE-B.

At step S41, UE-B sends a communication packet to UE-A. In step S42, UE-A determines the contracted carrier of UE-B based on the MAC address of the communication packet and Table 2, and refers to Table 1 to confirm that the PLMNID of the contracted carrier is the slice accommodation permission PLMNID. If so, accommodate the UE-B in the corresponding network slice. On the other hand, if the PLMNID of the contracted carrier of UE-B is not included in the slice accommodation permission PLMNID, the corresponding network slice does not accommodate UE-B. Also, when the PLMNID of the contracted carrier of UE-B is the Forbidden PLMNID received in step S14, UE-B is not accommodated in the corresponding network slice.

In step S43, when UE-B is accommodated in a network slice, the communication packet transmitted from UE-B is analyzed and accommodated in an appropriate network slice. Table 6 is an example of Table 3 created, stored and updated by UE-A in step S43.

As shown in Table 6, "S-NSSAI", "PDU session" and "connection terminal ID (MAC address)" are associated and stored. "S-NSSAI" corresponds to each network slice "Slice#n". "PDU session" identifies a PDU session established in the corresponding Slice #n. “Connection terminal ID (MAC address)” is the MAC address included in the communication packet. Multiple MAC addresses may correspond to one PDU session as in Slice #3. UE-A refers to Table 3 to identify the "PDU session" corresponding to the "connected terminal ID (MAC address)" of the communication packet received from UE-B.

In step S44, UE-A relays UE-B's communication packets to UPF using the PDU session. That is, UE-A sends communication packets received from UE-B to UPF, and communication packets received from UPF to UE-B.

According to the above-described embodiment, user equipment 20 can be accommodated in a network slice by relaying communication packets of other user equipment 20 in network services provided by carriers with which the user equipment 20 does not have a contract. It can communicate with a DN to utilize network services.

That is, it is possible to facilitate user network connectivity for operators that do not employ a roaming architecture.

(Device configuration)
Next, functional configuration examples of the network node 10 and the user device 20 that execute the processes and operations described above will be described. The network node 10 and the user equipment 20 include functionality to implement the embodiments described above. However, each of the network node 10 and the user device 20 may have only part of the functions in the embodiment.

<Network node 10>
FIG. 4 is a diagram showing an example of the functional configuration of the network node 10. As shown in FIG. As shown in FIG. 4 , network node 10 has transmitter 110 , receiver 120 , setter 130 , and controller 140 . The functional configuration shown in FIG. 4 is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functional division and the names of the functional units may be arbitrary. Also, the network node 10 having multiple different functions on the system architecture may be composed of multiple network nodes 10 separated for each function.

The transmitter 110 includes functions for generating signals to be transmitted to the user equipment 20 or other network nodes 10 and wirelessly transmitting the signals. The receiving unit 120 includes a function of receiving various signals transmitted from the user equipment 20 and acquiring, for example, higher layer information from the received signals. The transmission unit 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, DL reference signals, etc. to the user equipment 20 .

The setting unit 130 stores preset setting information and various types of setting information to be transmitted to the user device 20 in a storage device, and reads them from the storage device as necessary. The content of the setting information is, for example, information related to network registration.

The control unit 140 performs processing for registering the user device 20 in the network as described in the embodiment. Also, the control unit 140 performs processing related to establishment of a PDU session between the user equipment 20 and the user plane. A functional unit related to signal transmission in control unit 140 may be included in transmitting unit 110 , and a functional unit related to signal reception in control unit 140 may be included in receiving unit 120 .

<User Device 20>
FIG. 5 is a diagram showing an example of the functional configuration of the user device 20. As shown in FIG. As shown in FIG. 5 , the user device 20 has a transmitting section 210 , a receiving section 220 , a setting section 230 and a control section 240 . The functional configuration shown in FIG. 5 is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functional division and the names of the functional units may be arbitrary.

The transmission unit 210 creates a transmission signal from transmission data and wirelessly transmits the transmission signal. The receiving unit 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. The receiving unit 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL/SL control signals, reference signals, etc. transmitted from the network node 10 . Further, for example, the transmission unit 210, as D2D communication, to the other user apparatus 20, PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel) ), etc., and the receiving unit 220 receives PSCCH, PSSCH, PSDCH, PSBCH, or the like from the other user equipment 20 . Furthermore, the transmission unit 210 and the reception unit 220 have a transmission/reception function of wireless LAN or wired LAN.

The setting unit 230 stores various setting information received from the network node 10 or the user device 20 by the receiving unit 220 in the storage device, and reads the setting information from the storage device as necessary. The setting unit 230 also stores preset setting information. The content of the setting information is, for example, information related to network registration, information related to communication settings with other user devices, and the like.

The control unit 240 controls registration of the user device 20 to the network as described in the embodiments. The control unit 240 also establishes a PDU session and relays communication packets of other user devices 20 to the network. A functional unit related to signal transmission in control unit 240 may be included in transmitting unit 210 , and a functional unit related to signal reception in control unit 240 may be included in receiving unit 220 .

(Hardware configuration)
The block diagrams (FIGS. 4 and 5) used to describe the above embodiments show blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

Functions include judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't For example, a functional block (component) that makes transmission work is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, the network node 10, the user device 20, etc. according to the embodiment of the present disclosure may function as computers that perform processing of the wireless communication method of the present disclosure. FIG. 6 is a diagram showing an example of hardware configurations of the network node 10 and the user device 20 according to an embodiment of the present disclosure. The network node 10 and the user device 20 described above are physically configured as computer devices including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. may

In the following description, the term "apparatus" can be read as a circuit, device, unit, or the like. The hardware configuration of the network node 10 and the user device 20 may be configured to include one or more of each device shown in the figure, or may be configured without some of the devices.

Each function in the network node 10 and the user device 20 is performed by the processor 1001 by loading predetermined software (program) on hardware such as the processor 1001 and the storage device 1002, and controlling communication by the communication device 1004. or by controlling at least one of reading and writing data in the storage device 1002 and the auxiliary storage device 1003 .

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, the control unit 140 , the control unit 240 and the like described above may be implemented by the processor 1001 .

The processor 1001 also reads programs (program codes), software modules, data, or the like from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 140 of the network node 10 shown in FIG. 4 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Also, for example, the control unit 240 of the user device 20 shown in FIG. Although it has been explained that the above-described various processes are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

The storage device 1002 is a computer-readable recording medium. For example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured. The storage device 1002 may also be called a register, cache, main memory (main storage device), or the like. The storage device 1002 can store executable programs (program code), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

The auxiliary storage device 1003 is a computer-readable recording medium, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu -ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like. Auxiliary storage device 1003 may also be referred to as an auxiliary storage device. The storage medium described above may be, for example, a database, server, or other suitable medium including at least one of storage device 1002 and secondary storage device 1003 .

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like, for example, in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). may consist of For example, a transmitting/receiving antenna, an amplifier section, a transmitting/receiving section, a transmission line interface, etc. may be implemented by the communication device 1004 . The transceiver may be physically or logically separate implementations for the transmitter and receiver.

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Devices such as the processor 1001 and storage device 1002 are connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between devices.

In addition, the network node 10 and the user device 20 are hardware such as microprocessors, digital signal processors (DSPs), ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), and FPGAs (Field Programmable Gate Arrays). hardware, and part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

(Summary of embodiment)
As described above, according to the embodiments of the present invention, a communication unit that communicates with another user device, and a control unit that determines whether the other user device is connectable to a network slice a transmitting unit configured to transmit a communication packet transmitted from the other user device to the network slice when the other user device is connectable to the network slice; and the other user device is connectable to the network slice. a receiving unit for receiving communication packets to be transmitted from the network slice to the other user equipment.

With the above configuration, user equipment 20 can be accommodated in a network slice by relaying communication packets from other user equipment 20 in network services provided by carriers with which the user equipment 20 does not have a contract. You can use network services by communicating with That is, it is possible to facilitate user network connectivity for operators that do not employ a roaming architecture.

In the determination, if the PLMN (Public Land Mobile Network) ID notified from the other user device matches the PLMN ID connectable to the network slice acquired during the network registration process, the other user device It may be determined that the network slice is connectable. This configuration allows user equipment 20 to relay connections to network slices only to user equipment 20 with an authorized PLMNID.

The PLMNID that can be connected to the network slice acquired during the network registration process includes S-NSSAI (Single Network Slice Selection Assistance Information) that identifies the network slice, the port number of the communication packet, and the DSCP (Differentiated Services Code Point) of the communication packet. ) value, the IP (Internet Protocol) address of the communication packet, or the FQDN (Fully Qualified Domain Name) of the communication packet. With this configuration, the user device 20 can determine the user device 20 that can be connected to the network slice by associating and holding the network slice and the PLMN ID that is permitted to be accommodated.

The PLMNID notified from the other user device may be held in association with the MAC (Media Access Control) address of the other user device. With this configuration, the user device 20 can identify the user device 20 based on the MAC address of the communication packet and relay the communication packet to the network slice.

A network slice for transmitting the communication packet may be determined based on the MAC address included in the communication packet transmitted from the other user device. With this configuration, the user device 20 can identify the network slice to be connected based on the MAC address of the communication packet and relay the communication packet to the network slice.

Further, according to the embodiment of the present invention, a receiving unit that receives from a user device a communication packet transmitted from another user device to a network slice, and a communication packet that is transmitted from the network slice to the other user device A network node is provided that includes a transmission unit that transmits to the user device, and a control unit that notifies the user device of a PLMN (Public Land Mobile Network) ID connectable to the network slice.

With the above configuration, user equipment 20 can be accommodated in a network slice by relaying communication packets from other user equipment 20 in network services provided by carriers with which the user equipment 20 does not have a contract. You can use network services by communicating with That is, it is possible to facilitate user network connectivity for operators that do not employ a roaming architecture.

(Supplement to the embodiment)
Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art can understand various modifications, modifications, alternatives, replacements, and the like. be. Although specific numerical examples have been used to facilitate understanding of the invention, these numerical values are merely examples and any appropriate values may be used unless otherwise specified. The division of items in the above description is not essential to the present invention, and the items described in two or more items may be used in combination as necessary, and the items described in one item may be used in another item. may apply (unless inconsistent) to the matters set forth in Boundaries of functional or processing units in functional block diagrams do not necessarily correspond to boundaries of physical components. The operations of a plurality of functional units may be physically performed by one component, or the operations of one functional unit may be physically performed by a plurality of components. As for the processing procedures described in the embodiments, the processing order may be changed as long as there is no contradiction. Although the network node 10 and the user device 20 have been described using functional block diagrams for convenience of process description, such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor possessed by the network node 10 according to the embodiment of the present invention and the software operated by the processor possessed by the user device 20 according to the embodiment of the present invention are respectively stored in random access memory (RAM), flash memory, read-only memory. It may be stored in memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other appropriate storage medium.

Also, notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.Also, RRC signaling may be called an RRC message, for example, RRC It may be a connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message, or the like.

Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other suitable systems and extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

The procedures, sequences, flow charts, etc. of each aspect/embodiment described herein may be interchanged as long as there is no inconsistency. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

Certain actions described herein as being performed by a network node 10 may also be performed by its upper nodes. In a network of one or more network nodes, including network node 10, various operations performed for communication with user equipment 20 may be network node 10 and other network nodes other than network node 10. (eg, but not limited to MME or S-GW, etc.). Although the above example illustrates the case where there is one network node other than the network node 10, the other network node may be a combination of a plurality of other network nodes (for example, MME and S-GW). .

Information, signals, or the like described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). It may be input and output via multiple network nodes.

Input/output information and the like may be stored in a specific location (for example, memory), or may be managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.

The determination in the present disclosure may be performed by a value represented by 1 bit (0 or 1), may be performed by a boolean value (Boolean: true or false), or may be performed by comparing numerical values (e.g. , comparison with a predetermined value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

Software, instructions, information, etc. may also be sent and received over a transmission medium. For example, the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create websites, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.

Information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

The terms explained in this disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, the channel and/or symbols may be signaling. A signal may also be a message. A component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indexed.

The names used for the parameters described above are not limiting names in any way. Further, the formulas, etc., using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are in no way restrictive names. is not.

In the present disclosure, “base station (BS)”, “radio base station”, “base station device”, “fixed station”, “NodeB”, “eNodeB (eNB)”, “gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission/reception point", "cell", "sector", Terms such as "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station may serve one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being associated with a base station subsystem (e.g., an indoor small base station (RRH: The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem serving communication in this coverage. point to

In this disclosure, terms such as “Mobile Station (MS),” “user terminal,” “User Equipment (UE),” “terminal,” etc. may be used interchangeably. .

A mobile station is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of a base station and a mobile station may be called a transmitter, a receiver, a communication device, and the like. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between a plurality of user devices 20 (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). Each aspect/embodiment of the present disclosure may be applied to such a configuration. In this case, the user device 20 may have the functions of the network node 10 described above. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, user terminals in the present disclosure may be read as base stations. In this case, the base station may have the functions that the above-described user terminal has.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Judgement", "determining" are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as "judged" or "determined", and the like. Also, "judgment" and "determination" are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment" or "decision" has been made. In addition, "judgment" and "decision" are considered to be "judgment" and "decision" by resolving, selecting, choosing, establishing, comparing, etc. can contain. In other words, "judgment" and "decision" may include considering that some action is "judgment" and "decision". Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being "connected" or "coupled." Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in this disclosure, two elements are defined using at least one of one or more wires, cables, and printed electrical connections and, as some non-limiting and non-exhaustive examples, in the radio frequency domain. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.

The reference signal may be abbreviated as RS (Reference Signal), or may be referred to as Pilot according to the applicable standard.

As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly specified otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to elements using the "first," "second," etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.

The “means” in the configuration of each device described above may be replaced with “unit”, “circuit”, “device”, or the like.

Where "include," "including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

A radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe. A subframe may also consist of one or more slots in the time domain. A subframe may be of a fixed length of time (eg, 1 ms) independent of numerology.

A numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, transceiver It may indicate at least one of certain filtering operations performed in the frequency domain, certain windowing operations performed by the transceiver in the time domain, and/or the like.

A slot may consist of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots and symbols all represent units of time in which signals are transmitted. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations.

For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, and one slot or minislot may be called a TTI. may That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user equipment 20) to each user equipment 20 on a TTI basis. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit of channel-encoded data packets (transport blocks), code blocks, codewords, or the like, or may be a processing unit of scheduling, link adaptation, or the like. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a duration of 1 ms may also be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, and so on. A TTI that is shorter than a regular TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and so on.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the numerology, and may be 12, for example. The number of subcarriers included in an RB may be determined based on numerology.

Also, the time domain of an RB may include one or more symbols and may be 1 slot, 1 minislot, 1 subframe, or 1 TTI long. One TTI, one subframe, etc. may each consist of one or more resource blocks.

Note that one or more RBs are physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, and the like. may be called.

Also, a resource block may be composed of one or more resource elements (RE: Resource Element). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A Bandwidth Part (BWP) (which may also be referred to as a Bandwidth Part) may refer to a subset of contiguous common resource blocks (RBs) for a numerology on a carrier. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or multiple BWPs may be configured for a UE within one carrier.

At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

The structures such as radio frames, subframes, slots, minislots and symbols described above are exemplary only. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, the Cyclic Prefix (CP) length, etc. can be varied.

In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include the plural nouns following these articles.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching according to execution. In addition, the notification of predetermined information (for example, notification of “being X”) is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.

Note that the transmitting unit 210 and the receiving unit 220 in the present disclosure are an example of a communication unit. UE registration is an example of a network registration process.

Although the present disclosure has been described in detail above, it should be apparent to those skilled in the art that the present disclosure is not limited to the embodiments described in this disclosure. The present disclosure can be practiced with modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not meant to be limiting in any way.

10 network node 110 transmitting unit 120 receiving unit 130 setting unit 140 control unit 20 user device 210 transmitting unit 220 receiving unit 230 setting unit 240 control unit 1001 processor 1002 storage device 1003 auxiliary storage device 1004 communication device 1005 input device 1006 output device

Claims (3)

a communication unit that communicates with other terminals ;
a control unit that determines whether the other terminal is connectable to the network slice;
a transmission unit configured to transmit a communication packet transmitted from the other terminal to the network slice when the other terminal is connectable to the network slice;
a receiving unit that receives a communication packet to be transmitted from the network slice to the other terminal when the other terminal is connectable to the network slice ;
In the determination, if the PLMN (Public Land Mobile Network) ID notified from the other terminal matches the PLMN ID connectable to the network slice acquired during the network registration process, the other terminal is connected to the network determine that the slice is connectable,
hold the PLMNID notified from the other terminal in association with the MAC (Media Access Control) address of the other terminal;
A terminal that determines a network slice for transmitting a communication packet based on the MAC address included in the communication packet transmitted from the other terminal . The PLMNID that can be connected to the network slice acquired during the network registration process includes S-NSSAI (Single Network Slice Selection Assistance Information) that identifies the network slice, the port number of the communication packet, and the DSCP (Differentiated Services Code Point) of the communication packet. ) value, an IP ( Internet Protocol) address of a communication packet, or an FQDN (Fully Qualified Domain Name) of a communication packet, and is held in association with the communication packet. a procedure for communicating with other terminals;
a procedure for determining whether the other terminal is connectable to the network slice;
a step of transmitting a communication packet transmitted from the other terminal to the network slice if the other terminal is connectable to the network slice;
a step of receiving a communication packet to be transmitted from the network slice to the other terminal when the other terminal is connectable to the network slice;
In the determination, if the PLMN (Public Land Mobile Network) ID notified from the other terminal matches the PLMN ID connectable to the network slice acquired during the network registration process, the other terminal is connected to the network a procedure for determining that the slice is connectable;
A procedure for holding the PLMNID notified from the other terminal in association with the MAC (Media Access Control) address of the other terminal;
A communication method in which a terminal executes a procedure of determining a network slice for transmitting a communication packet based on the MAC address included in the communication packet transmitted from the other terminal.

Images